Microservices Health

Log ID Level Message Cause Remedy Impact
4001 Info Health monitoring port not configured Health monitoring port not configured None Health monitoring not supported
4002 Info Starting health monitoring on port %v Health monitoring started on this port None None
4003 Fatal Failed to process microservice configuration file File does not exist or has errors Report issue to Extreme Networks support Service not started
4004 Info Go Version: [%s], OS/Arch: [%s/%s] Go version and architecture information None None
4005 Info Starting microservice [%s] Microservice starting None None
4006 Info [%s]: Worker Shutdown started Service shutdown stops each worker thread None Service unavailable until restarted
4007 Info [%s]: Worker Shutdown done Worker thread stopped successfully None Service unavailable until restarted
4008 Info Starting Shutdown of Microservice, received signal Microservice shutting down None Service unavailable until restarted
4009 Error Completed shutting down all worker threads, exiting Microservice shutdown completed None Service unavailable until restarted
4010 Info [%s]: Worker Started New worker thread starting None None
4011 Info Starting Watchdog processing Watchdog worker thread starting None None
4012 Error [%s]: Microservice is dead Microservice not responding to the watchdog Service stopped or malfunctioning; restart service Service may not be responding
4013 Warning [%s]: Service already dead Service already stopped None None
4014 Warning [%s]: Watchdog state unknown Incorrect value received in message Retry the command or configuration; report issue to Extreme Networks support if persistent Command or config failed to apply and was ignored
4015 Info Watchdog Starting Watchdog worker thread starting None None
4016 Error K3S Liveliness check failed Microservice seems unresponsive If issue persists, restart service Service is unavailable
4017 Error K3S Readiness check failed Service still instantiating or failed If issue persists, restart service Service is unavailable
4018 Panic Panic Service encountered unrecoverable error Report issue to Extreme Networks support Service will be restarted
4019 Fatal Fatal error Service encountered unrecoverable error Report issue to Extreme Networks support Service will be restarted
4020 Error Failed to resolve host IP: %s Configuration file may be missing Report issue to Extreme Networks support Service may not function correctly
4021 Info Completed setting up pprof for %v with %v interval, %v allowed archives Profiling started for service None Periodic pprof collection for service
4022 Error Failed to set up pprof for %v with %v interval, %v allowed archives Profiling started for service Report issue to Extreme Networks support Periodic prof collection for service unavailable
4023 Error Failed to process gNMI/gRPC notification Notification may have unexpected or invalid data Report issue to Extreme Networks support Service may not function as expected
4024 Error Memory read failure Virtual memory issue Report issue to Extreme Networks support Inconsistent memory information
4025 Warning High memory usage Memory consumption above threshold Report issue to Extreme Networks support Service may recover or fail after some time elapses
4026 Error File read failure Invalid or inaccessible path/file Report issue to Extreme Networks support Inconsistent file or disk information
4027 Error Platform component property processing failed Invalid or unexpected platform component key/path Report issue to Extreme Networks support Service may not function as expected
4028 Fatal Requisite flags for db migration app not set; cannot proceed, exiting. Requisite flags for db migration app not set Report issue to Extreme Networks support DB migration service launch fails
4029 Fatal Fatal error DB migration encountered error Report issue to Extreme Networks support Service may not function as expected